Digital asset data type definitions

ABSTRACT

Data definitions for digital assets, such as, for example, audio, video, photographs, graphics, and electronic documents, are provided that allow these different asset types to be stored in a single database. The definitions are preferably in XML and can be used as a standardized dictionary to more efficiently and economically manage digital-assets, thus improving system interoperability between companies or organizations within a company. A digital asset ordering interface, hardware system, software arrangement, and application interface configuration advantageously using these data definitions are also provided.

CROSS REFERENCE TO RELATED APPLICATION

This claims the benefit of U.S. Provisional Application No. 60/254,991,filed Dec. 12, 2000.

BACKGROUND OF THE INVENTION

This invention relates to storing, retrieving, and tracking digitaldata. More particularly, this invention relates to data definitions thatallow disparate types of digital assets, such as, for example,photographs, graphics, audio, video, and text documents, to be easilyand economically stored, retrieved, and tracked.

Data definitions may be written using XML (extensible markup language).XML is a condensed form of SGML (standard generalized markup language),which is an information management standard that provides documents thatretain formatting, indexing, and linked information—independent ofapplication and platform. XML and SGML can be used to organize andpresent information on the World Wide Web.

Many companies maintain or access large libraries of various audio,visual, and textual assets. Such assets typically include content andmetadata. Content may be, for example, still photographs, audiorecordings, video recordings, combined audio/video recordings, combinedaudio/still photograph recordings, graphics, etc. Metadata is“information about information,” that is, information used to identifyor classify the content. Metadata can include, for example, contenttitles, version numbers, authors, captions, and other descriptiveinformation relevant to the content.

Such assets are often stored in disparate repositories and on disparatemedia (e.g. audio and video cassette tapes, motion picture film,photographic negatives, digital video discs, etc.). Accordingly, asignificant amount of time is often required to locate a particularasset and then deliver a copy of it. For example, it may take severaldays to locate and manually copy an audio track stored on a reel-to-reeltape located at a creative services or marketing department of a companyin California and then have that copy shipped to a business affairsdepartment or sister company in New York. This process, known asrepurposing, is manually intensive and prone to errors. Furthermore,keeping track of asset usage (e.g., who has asset copies) is also amanually intensive process prone to errors. Accordingly, it can costthousands or even millions of dollars annually for a company to managesuch assets.

In an attempt to reduce these costs, some companies store assetsdigitally in one or more computer databases. These assets can then beretrieved electronically using appropriate software applications.However, known applications are limited. For example, databases arecommonly structured to store only one type of digital asset, such as,for example, only photographs. The number, size, and formats of recordfields used in the database, characters delimiting the end of files,file size of database records, etc. are all usually customized (andlimited) to that one type of asset. Even those few databases that areknown to store more than one asset type are also limited with respect torecord field definitions and record file size, making them incompatiblefor use with many other types of digital assets. Such databases are thusimpractical for storing a large variety of different types of digitalassets.

In sum, storing disparate asset types in a single repository havinginformation and formatting sufficient for identification and retrievalby a single software application or computer platform is not known.Moreover, no standardized definitional dictionary for digital assets isknown. Thus, system interoperability between two or more companies ortwo or more organizations within a company having different types ofdigital assets is still very difficult.

In view of the foregoing, it would be desirable to be able to provide astandardized dictionary of data definitions for disparate types ofdigital assets.

It would also be desirable to be able to provide data definitions forapplication and platform independent search, retrieval, delivery, andtracking of digital assets.

It would further be desirable to be able to provide data definitionsthat reduce digital asset search time.

It would still further be desirable to be able to provide datadefinitions that reduce digital asset delivery time.

SUMMARY OF THE INVENTION

It is an object of this invention to provide a standardized dictionaryof data definitions for disparate types of digital assets.

It is also an object of this invention to provide data definitions forapplication and platform independent search, retrieval, delivery, andtracking of digital assets.

It is a further object of this invention to provide data definitionsthat reduce digital asset search time.

It is a still further object of this invention to provide datadefinitions that reduce digital asset delivery time.

In accordance with this invention, data definitions are provided fordigital assets that include a hierarchical structure that reflects therelationships between attributes and categories of content. Thesedefinitions, preferably encoded in XML, can be used as a standardizeddictionary to create a digital asset library that is easily andeconomically manageable. The data definitions are applicable to digitalassets of disparate data types and include metadata identifierssufficient to uniquely identify those digital assets.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects and advantages of the invention will beapparent upon consideration of the following detailed description, takenin conjunction with the accompanying drawings, in which like referencecharacters refer to like parts throughout, and in which:

FIG. 1 is a flow chart of an interface for ordering digital assets usingdata definitions according to the invention;

FIG. 2 is a block diagram of an embodiment of a hardware system withinwhich the invention can be used;

FIG. 3 is a block diagram of an embodiment of integrated softwareaccording to the invention;

FIG. 4 is a block diagram of an embodiment of an application interfaceconfiguration according to the invention;

FIG. 5 shows an embodiment of a display screen for asset searchingaccording to the invention;

FIG. 6 shows an embodiment of a display screen for search resultsaccording to the invention; and

FIG. 7 is a high level block diagram showing an embodiment of a documenttype definition (DTD) for digital assets according to the invention.

DETAILED DESCRIPTION OF THE INVENTION

The invention provides data definitions, preferably in XML, fordisparate types of digital assets, such as, for example, artwork, logos,photographs, video, graphics, music, still photographs, promotionstills, promos (e.g., an audio or video promotional announcement),tapes, soundtracks, text, video frames (a single image from a videorecording), video clips (a group of images from a video recording), anddailies (unedited and unprocessed video or film typically recorded theprevious day). Digital assets include content (i.e., the actual assetdata) and metadata. Data definitions of the invention advantageouslypermit a single database to be used for storing, retrieving, andtracking different types of assets whose contents are preferably storedeither on the same computer as the database, in the database, on acomputer linked to the database via the same network, or combinationsthereof. These data definitions allow, for example, employees,affiliates, and customers to relatively easily and economicallyreplicate or transfer assets between repositories where the assets arelocated and destinations where the assets are currently needed.Furthermore, electronic records can be created to allows usage of thoseassets to be easily tracked. Thus, the costs associated with managingthose assets are significantly reduced.

FIG. 1 shows an interface for searching and ordering digital assetsfacilitated by the invention. System Home Screen 101 is preferably thefirst screen a user views when searching for a digital asset (e.g., avideo program). While at Home Screen 101, users may enter searchcriteria before proceeding to another screen. However, this isalternatively not necessary. From Home Screen 101, the user may proceedin one of the following ways: along path 102 to Login Screen 103, alongpath 104 to Register Screen 105, along path 106 to Advanced SearchScreen 107, along path 108 to Top Picks Screen 109, along path 110 toLatest Releases Screen 111, or along path 112 to Editor's Choice Screen113.

At Login Screen 103, users login to a secured version of a search systemassociated with interface 100. A user entering Login Screen 103 alongpath 102 is preferably directed along path 114 to User Home Screen 115unless the user entered search criteria while viewing Home Screen 101.In that case, the user is preferably directed to Order Confirmation andDownload Screen 117 along path 116. Similarly, if the user entered LoginScreen 103 along path 127, the user is also preferably directed to OrderConfirmation and Download Screen 117.

At Register Screen 105, users register to use the system. Users may beassigned or may freely choose a username, password, and any otherrelevant identifying information. Users may be prompted by RegisterScreen 105 to enter information deemed relevant or necessary by thesystem. After registering, users are preferably directed along path 118to User Home Screen 115.

At Advanced Search Screen 107 users enter or are given pre-definedcriteria with which the database of the invention can be searched.Screen 107 preferably allows users to generate advanced search criteriaincluding, but not limited to, searching specific strings, numericvalues, fields or combinations of fields containing data, as well asallowing users to define complex or simple search expressions usingboolean or other logic, wildcards, multiple search criteria, or anyother type of search functionality. Preferably, upon an indication by auser or upon a pre-defined system event (for example, expiration of atimer), a user will be directed along path 119 to Search Results Screen120.

At Top Picks Screen 109, a user can view and select from a subset ofassets defined in the database. This subset may be predefined by theuser, the system, or a system administrator. The subset may be definedas the most viewed assets, most searched for assets, most retrievedassets, most popular assets, or top assets based on a criteria definedby a user, the system, or an administrator.

At Latest Releases Screen 111, a user can view and select from a subsetof assets in the database This data is preferably a subset of the mostrecently added assets in the database. However, the subset may bedefined as the most recently released assets, most recently producedassets, or any other desired subset of data in the database.

At Editor's Choice Screen 113, a user can view and select from a subsetof assets defined in the database. This subset is preferably a selectionof assets that one or more editors, within the company or organizationviewing or providing the database, has selected as being desirable forviewing based on one or more criteria defined by the editors.

At User Home Screen 115, a user can view personalized or standardinformation relating to that user's usage of the database. The systemmay present the user with search possibilities, the ability to view somesubset of assets defined in the database, a listing of data that may beuseful in some respect, and any other relevant information or functionalpossibilities. Preferably, upon an indication by a user or upon apre-defined system event (for example, expiration of a timer), the useris directed along path 122 to Content Detail Screen 123.

At Search Results Screen 120, a user can view and select from a subsetof data retrieved in accordance with criteria defined by the user whileviewing Advanced Search Screen 107 and possibly in accordance with oneor more database enforced criteria. Upon indicating a selection of oneor more assets, a user is directed along path 121 to Content DetailScreen 123.

In addition to being directed along path 121 or 122 as described, a usermay be directed along path 124 from any of screens 109, 111, or 113 toContent Detail Screen 123. A user may be automatically directed toscreen 123 if a small number of asset definitions are the only items theuser wishes to view. For instance, if a user performs a complex searchand the system finds only one asset satisfying the search criteria, thesystem may automatically bypass Search Results Screen 120 and displayContent Detail Screen 123.

At Content Detail Screen 123, a user can view all or part of the summarydata directly related to one or more items selected manually orautomatically by the user. Preferably, upon an indication by the user orupon a pre-defined system event (for example, expiration of a timer), auser is directed along path 125 to Order Options Screen 126.

At Order Options Screen 126, a user can view and select from optionsrelated to ordering and downloading data for which summary data wasviewed while viewing Content Detail Screen 123. These options mayinclude billing, routing, formatting, data transmission, delivery date,delivery time, and other relevant options. Upon indication by a user orupon a pre-defined system event, the user is directed along path 127 toLogin Screen 103 or along path 128 to Order Confirmation And DownloadScreen 117. Preferably, a user is directed along path 127 when the userhas not logged in using Login Screen 103. Alternatively, a user isdirected along path 128 when the user had previously logged in via LoginScreen 103. In some systems, logging in is not necessary. In othersystems, a user that has logged in but has not taken any decisive action(for instance, has not made an indication at Order Options Screen 126within a specified amount of time after logging in) is directed alongpath 127.

At Order Confirmation And Download Screen 117 the system preferablydisplays details and summary information relating to an asset that wasordered by a user. The user is preferably presented with the opportunityto download or retrieve the asset. Such retrieval may be performedeither electronically or by using devices (such as printers, taperecorders, compact disc writers, digital video disc writers, or otherrecording or printing equipment) to convert an asset stored in adatabase or in an associated or networked computer memory to a digitalor analog item stored in another manner.

Note that any of paths 102, 104, 106, 108, 110, 112, 114, 116, 118, 119,121, 122, 124, 125, or 128 may be traversed in reverse by users thatwish to step backwards in the search and ordering process. Also,securing the search system is not a necessary function of the invention.Note further that all of interface 100 is not necessary for implementingthe invention; an interface employing even a very small subset ofinterface 100 can benefit from the invention. Moreover, additionalprocess paths and functionality (for instance, paths connecting any ofscreens 109, 111, 113, 115, and 123 directly to Search Results Screen120 to allow a user to view search results from a search performed whileviewing any of those screens) can be added to interface 100.

In sum, the data definitions of the invention enable systems usinginterface 100 or similar interfaces to provide satisfactory interactivesearch and response times to users.

FIG. 2 shows a hardware system 200 that can be used to manage digitaldata defined with data definitions in accordance with the invention.System 200 preferably includes one or more servers 201, a securetransmission line 202, at least one secure recording or printing device203, one or more secure access devices (e.g., laptop 204, computer 205,and workstation 206), at least one firewall 207, one or more non-securetransmission lines 208, one or more non-secure access devices (e.g.,computer 209, workstation 210, and laptop 211), and at least onenon-secure recording or printing device 212.

One or more servers 201 store all or part of one or more databases.Servers 201 may be accessed via secure transmission line 202 by secureaccess devices 204-206 or by firewall 207 which has received appropriateindications from non-secure access devices 209-211 via non-securetransmission line 208. Upon receiving appropriate indications fromdevices 204-206 or firewall 207, servers 201 transmit data to devices204-206, firewall 207, or recording or printing device 203, asappropriate, via secure transmission line 202.

Upon receiving appropriate indications (based on security criteria),firewall 207 transmits data to non-secure access devices 209-211 ornon-secure recording or printing device 212, as appropriate, vianon-secured data transmission line 208.

Secure access devices 204-206 and non-secure access devices 209-211 caninclude laptop computers, desktop computers, and workstations (asshown), as well as other types of terminals, wireless devices, personaldigital assistants (PDAs), television set-top boxes, other databases,and other digital devices that can receive user indications and cancommunicate with servers or firewalls.

Severs 201 can be, for example, Sun® servers using the Solaris®platform, Oracle database servers, or any other appropriate serverplatform. Transmission lines 202 and 208 may use T-1, T-2, or any otherappropriate transmission standards. Alternatively, the invention can bepracticed with a configuration as simple as a single computer that cando the following: store and query a database in its RAM, ROM, hard diskdrive, compact disc, floppy disk, or other suitable storage medium;display visual or play audio content; and receive user indications.

FIG. 3 shows an embodiment of integrated software according to theinvention. Computer 301 (which may be any of secure access devices204-206, firewall 207, and non-secure access devices 209-211)communicates with servers 201. Project applications 303, which arepreferably encoded in XML, transmit a demand 304 for databaseinformation to database 305. Database 305 may be, for example, Oracle®,Sybase®, Microsoft Access®, or any other relational or non-relationaldatabase package. Database 305 creates preferably XML files 306. Anexample of an XML file 306 is shown in Example 2 below. XML files 306are transmitted in. HTML format 307 a for viewing graphics with abrowser 308. Microsoft Internet Explorer® and Netscape Navigator® aretwo examples of browsers that may be used. Preferably, format 307 a isHTML with cascading style sheets (CSS).

Alternatively, XML files 306 may be transmitted in XML format 307 b foruse by other applications 309, such as, for example, C, C++, or Javaapplications that may be for a stand-alone screen, front-end GUI, or Webpresentation package. Alternative format 307 b may include XML with CSSfor further processing by applications such as search engines or bots ormay include regular HTML if a still or active display is the only outputrequirement. Bots are programs that typically perform repetitive or timeconsuming tasks on a network (e.g., searching Web sites on theInternet). Examples of formats 307 a and 307 b are shown below inExamples 3a-c.

FIG. 4 shows an embodiment of an application interface configuration inaccordance with the invention. In this configuration, a user providessearch parameters 401 to client application 402, which is active oncomputer 301. Client application 402 converts search parameters 401 intoa demand 304 for database information. Demand 304 may take the form ofan SQL (structured query language) query when database 305 is anSQL-based relational database. Preferably, however, server 201 processesdemand 304 in a server application 404. Server application 404preferably includes the following modules; an XML parser 414, an XSLprocessor 424, and an XML-SQL utility 434. XSL (extensible style sheetlanguage) is a language for specifying style sheets that applyformatting to complex XML data for presentation in HTML and otherformats. XSL can map a single XML element to more than one type ofdisplay object (e.g., both an element in a list and an item in a table).A style sheet is a text file containing code to apply semantics such aspage layout specifications to an HTML document.

After converting demand 304 to SQL format (if necessary depending on thedatabase), application 404 sends query 405 to database 305. Database 305processes query 405 and returns search results 406 to application 404.Application 404 then processes results 406 to create one or more XMLfiles. These XML files are sent by application 404 as data 407 to XSLstyle sheet 408. XSL style sheet 408 processes data 407 and returns aresponse 307 in format 307 a or 307 b, as appropriate. Clientapplication 402 then converts response 307 into a format that can beheard or viewed by the user.

FIG. 5 shows an example of a display that can be used as Advanced SearchScreen 107. Illustrative display 501 includes interactive features 502,503, 504, and 505. Display 501 may alternatively include more or lessinteractive features as appropriate for a given implementation of theinvention. Interactive feature 502, entitled “PLEASE ENTER KEYWORDS TOSEARCH,” accepts user entries of keywords or phrases to be used by XMLproject applications 303 when forming demand 304. For example, “Oscarbelt” may be entered via interactive feature 502 by a user searching fora picture that has metadata containing the description, “Oscar Delahoyawearing a championship belt.” Interactive feature 503, entitled “PLEASESELECT ASSET CATEGORY,” accepts user entries for the type of asset toretrieve. For example, possible asset types are photos, audio, video,text, any combination of these, or any other appropriate asset type.Interactive feature 504, entitled “SEARCH,” allows users to submit asearch request (i.e., have application 303 form a demand 304).Interactive features 505, entitled “DTD,” “XML,” “XSL,” and “XSL SS,”allow a user to select a source code format in which to view datainstead of viewing a composes video screen or hearing a composed audiooutput.

FIG. 6 shows an example of a display that can be used as Search ResultsScreen 120. In this example, illustrative display 601 indicates at 602that 4 photo assets, 1 video asset, and 1 audio asset had been found,and shows at 603 a list of photographic assets, that met the criteria ofa demand 304. Illustrative display 601 preferably includes features 604,605, 606, and 607. Alternatively, display 601 can include more or lessfeatures as desired for a given implementation of the invention.Features 604 interactively accepts user indications of selection orrejection of assets from the displayed list of assets. Features 605 maybe interactive (e.g., a button) or static (e.g., just a display). Inthis example, feature 605 displays an image of the assets associatedwith the retrieved list items. If feature 605 is interactive, it canaccept a user's selection of an asset to be ordered. Feature 606displays descriptive information associated with the assets that met thecriteria of demand 304. Feature 606, like feature 605, may beinteractive to accept user selections of an asset. Feature 607, entitled“ORDER CHECKED,” is interactive and accepts indications that a user hasfinished selecting assets and is ready to proceed along path 121 toContent Detail Screen 123.

FIG. 7 shows an embodiment of a document type definition (DTD) inaccordance with the invention. A DTD is a separate file or document thatcontains formal definitions of all the data elements in a particulartype of XML (or HTML or SGML) document, such as a report or a book. Byconsulting the DTD for a document, a program called a parser (e.g., XMLparser 414) can work with the markup codes that the document contains.DTD 700 includes asset element 701, which defines the type of data to bestored for each digital asset. DTD 700 may also include one or moreother data elements 702 for other uses. For example, asset element 701can contain a core set of definitions, while data element 702 cancontain additional definitions that augment the core set in cases wheresuch additional definitions are required by a particular user.

Asset element 701 preferably includes asset metadata 703, asset typedata 704, and asset content 705. Asset element 701 may also includeadditional definitional information as desired. Asset metadata 703preferably includes the following definitional elements: productidentifier (ID) (e.g., a video program name), version ID, inventory ID,and ownership rights ID. Asset metadata 703 can also include any subsetof these identifiers or any additional identification information.

Asset type data 704 advantageously can include any number ofdefinitional elements relevant to a particular type of asset. Table 1 isa preferred embodiment of asset type data 704 in accordance with theinvention, showing definitional elements for classifying five assettypes:

TABLE 1 ASSET TYPE → Photo Movie Audio Promo Voiceovers Metadata AdSlick Version Music On-Line edit Announcer Agency Rating Stock Airmaster# Session Date Approved Minutes Library EE Master # 1st air date ArchiveSeconds Sub Library Textless # Residual payment Art Director Date CD #Writer/ Production Producer company Black/White AKA Title CD TitleDuration Agency Box ID Type Track Title Music Telephone # Caption GenreDuration Announcer Fed ID# Character Caption Composer Cut versionsAddress Client Title Publisher Graphics Color Licensor Society Promo DubComments Release Shoot Date Material Discard Date Rating Original EPKEntry Date Foreign Code Trailer Lang. Storage Date Run Time Title KillDate Department Color/BW Duration Comments Final art Director Session DTDAT Job number Cast Composer Script Licensor Brief Publisher EDLSynopsis Off-site P Version Society Screening storage Format notesPhotographer Synopsis Rights Internet Issues rights Product ID ProductID Contract (lic.) Poster Art Version ID Internet Press Kit Contract IDInternational Version ID Run code Library Contact Project SAP NumberResolution Restrictions Shoot date Talent Title

Note that the elements defined in Table 1 are illustrative and thus areneither required nor exclusive of other elements.

Asset content 705 preferably includes one of the following: digitallyencoded asset data, a link to a file containing asset data, or areference to a location where asset data is digitally stored.Alternatively and less preferable, multiple copies of a digital assetcan be referenced or included in asset content 705.

An embodiment of DTD 700 for digital assets, which includes assetelement 701, asset metadata 703, asset type data 704, and asset content705, is shown below in Example 1 in accordance with the invention.

EXAMPLE 1

<! -DTD FOR DIGITAL ASSETS -> <! -Digital Library Data Definition -> <!-Supporting technologies include but not limited to XML, XSL, XSLT,XPATH, DTD Schema-> <!ELEMENT digitalAsset (assetMetadata,movieTitleMetadata?, rightsMetadata, transactionMetadata?, Photo*,Promo*, Audio*, Movie*,)> <!ELEMENT assetMetadata (#PCDATA)> <! ATTLISTassetMetadata AssetTitle CDATA #IMPLIED this asset package has a nameAssetComments CDATA #REQUIRED comments/description about the asset groupAssetVersion CDATA #REQUIRED version, major + minor AssetCreateDateCDATA #REQUIRED create date > <!ELEMENT movieTitleMetadata (#PCDATA)> <!ATTLIST movieTitleMetadata PID CDATA #REQUIRED product id; link toPRIME.PPROD VID CDATA #REQUIRED PEG--version id; LINK TOprime/pversion_general RID CDATA #REQUIRED rights id, for FUTURE useGenre CDATA #REQUIRED PEG genre, may be several genres [ ] FUT makemultiple elements? Rating CDATA #REQUIRED PEG MPAA informationmovieTitleLong CDATA #REQUIRED PEG the movie title, full name with allpunctuation movieTitleShort CDATA #REQUIRED PEG abbreviated movie title,suitable for computer filenames; no blanks, special chars movieTitleAKACDATA #IMPLIED alternate movie name; different countries StudioProviderCDATA #IMPLIED PEG--copyright owner or provider of tape Director CDATA#REQUIRED PEG--movie director Cast CDATA #REQUIRED PEG cast members,talent [ ] FUT make multiple elements? SynopsisBrief CDATA #REQUIRED PEGshort description SynopsisLong CDATA #REQUIRED full descriptionLanguages CDATA #REQUIRED PEG languages; may be several on many tracks;[ ] FUT make multiple elements? movieComments CDATA #REQUIREDtransmission commentary information movieCreateDate CDATA #REQUIRED PEGneeds year creation date movieRun_Time CDATA #REQUIRED PEG hh:mmmovieRun_Time-Status CDATA #REQUIRED estimated or actualmovieRunTimeMinutes CDATA #IMPLIED RunTime minutes movieRunTimeSecondsCDATA #IMPLIED RunTime seconds Run_Code CDATA #IMPLIED (ex. 2:02 HA)Run_Code_Type CDATA #IMPLIED can include codes indicating type ofencoding etc. Color/BW CDATA #IMPLIED black & white or color CaptionCDATA #IMPLIED caption or description information Keywords CDATA#IMPLIED digital library query data for file retrieval > <!-RightsManagement Structure-> <!ELEMENT rightsMetadata (#PCDATA)> <! ATTLISTrightsMetadata CID CDATA #REQUIRED contract id Amend_No CDATA #IMPLIEDcontract amendment number Ravi_ID CDATA #IMPLIED rights availabilitywindow id Start_Date CDATA #IMPLIED PEG start of availability End_DateCDATA #IMPLIED PEG end of availability No_of_Plays CDATA #IMPLIEDallowed number of plays per agreement Usage_Allowed CDATA #IMPLIED extrarestrictions (ex. Rewind, pause, fast forward) Fee CDATA #IMPLIEDtransaction fee Authorized_Zone CDATA #IMPLIED geography or personWorld_Wide_Rights CDATA #IMPLIED yes or no Music_Effects CDATA #IMPLIEDyes or no (ex. train crash, explosion) Licensor CDATA #IMPLIED copyrightholder Coypright_Year CDATA #IMPLIED year of copyright > <!-TransactionMetadata Structure-> <!ELEMENT transactionMetadata (#PCDATA)> <! ATTLISTtransactionMetadata Trans_ID CDATA #REQUIRED transaction id Trans_TypeCDATA #IMPLIED type of transaction Trans_Date CDATA #IMPLIED date oftransaction Trans_User_ID CDATA #IMPLIED transaction author > <!-DigitalPhoto Metadata Structure-> <!ELEMENT Photo (photoMetadata,transactionMetadata)> <!ELEMENT photoMetadata (#PCDATA)> <! ATTLISTphotoMetadata <!-Baseline - Information Required fields-> BID CDATA#REQUIRED base ID Form_DigitalAsset CDATA #REQUIRED photographs,graphics, location stills, or royalty fee Orig Creation Date CDATA#REQUIRED original creation date of digital photo asset (date field)Resolution Type CDATA #REQUIRED <!-Production Information (extractedfrom PRIME)-> Film/Series/Program_Title CDATA #IMPLIED program titleassociated with photograph Orig Broadcast Date CDATA #IMPLIED originalbroadcast date of film or series (date field extracted from PRIME) OrigBroadcast Season CDATA #IMPLIED original broadcast season of program orseries Orig Release Date CDATA #IMPLIED original release date of programor series Film/Series_Creation Date CDATA #IMPLIED original creationdate of film or series (date field) Original Copyright Year CDATA#IMPLIED copyright year (date field Film/Series_Version CDATA #IMPLIEDversion control information Film/Series_Origin CDATA #IMPLIED origin offilm or series (e.g. HBO Theatrical) Description_Blurb CDATA #IMPLIEDdescription information extracted from PRIME Form_Program CDATA #IMPLIEDprogram type (e.g. Movie) Genre CDATA #IMPLIED program style (e.g.Romance, Drama, Comedy) Rating CDATA #IMPLIED program rating (e.g. R,PG) FilmSeries_Director CDATA #IMPLIED director of film or seriesFilm/Series_Writer CDATA #IMPLIED writer of film or seriesFilm/Series-Producer CDATA #IMPLIED producer of film or seriesFilm/Series_Cast Talent CDATA #IMPLIED film or series cast and talentinformation FilmSeries_Production CDATA #IMPLIED production executiveExecutive Film/Series Programming CDATA #IMPLIED programming executiveExecutive <!-Photograph Content Information-> Cast/Talent_Photo CDATA#IMPLIED cast or talent that appear in photograph Crew Name_Photo CDATA#IMPLIED crew that appear in photograph Crew Position_Photo CDATA#IMPLIED crew position (e.g. Director, Producer, Writer) Origin_PhotoCDATA #IMPLIED origin of photo (e.g. Warner Brothers, United Artist,Sports Illustrated) Agency CDATA #IMPLIED creative agency informationArt Director_Photo CDATA #IMPLIED Art Director information PhotographerCDATA #IMPLIED Photographer information Requesting Department CDATA#IMPLIED division requesting digital content Request Date CDATA #IMPLIEDdate of request for digital asset (date field) <!-Physical PhotographInformation-> Orig Photo ID CDATA #IMPLIED barcode information fromphoto label Orig Photo Medium CDATA #IMPLIED (e.g. negative, print,transparency) Orig Photo Location CDATA #IMPLIED location of photo inphysical archive Orig Photo Archive Date CDATA #IMPLIED original archivedate of photo (date field) Orig Photo Archive Box CDATA #IMPLIEDoriginal box number from physical file Number <!-General Information->DID CDATA #IMPLIED digital asset id. link to Artesia UO!_ID_(—) ShootType CDATA #IMPLIED type of photographic shoot (e.g. gallery, locationstill, acquisition) Color CDATA #IMPLIED color space of digital photo(e.g. black & white color) Description CDATA #IMPLIED description ofdigital photograph subject matter Comments CDATA #IMPLIED generalcomments Ready for Rights CDATA #IMPLIED yes or no Input Date CDATA#IMPLIED date of ingestion into Digital Library system (date field)Input By CDATA #IMPLIED name of person responsible for uploading assetinto Digital Library Last Updated Date CDATA #IMPLIED date of lastupdate or modification (date field) Last Updated By CDATA #IMPLIEDperson responsible for last update or modification <!-RightsInformation-> Asset Copyright Year CDATA #IMPLIED digital asset year ofcopyright Asset Copyright Holder CDATA #IMPLIED digital asset copyrightholder Restrictions_Legal CDATA #IMPLIED legal restrictions associatedwith digital asset Restrictions_Photographer CDATA #IMPLIED photographerrestrictions associated with digital asset Restrictions_Exclusives CDATA#IMPLIED yes or no Exclusives Held Until CDATA #IMPLIED expiration ofexclusive condition linked to digital asset (date field)Restrictions_License CDATA #IMPLIED licensing limitations orrestrictions Limitations associated to digital asset Legal Contact CDATA#IMPLIED legal contact for information regarding digital content usageAvailability End Date CDATA #IMPLIED date when digital asset is nolonger available for usage (date field) Rights Input Date CDATA #IMPLIEDdate digital rights entered into Digital Library system (date field)Rights Input By CDATA #IMPLIED person entering digital rights info intoDigital Library system Rights Last Updated Date CDATA #IMPLIED daterights information was last upgraded or modified (date field) RightsLast Updated By CDATA #IMPLIED person responsible for last update ormodification of rights info <!-Digital Photograph Information-> FilenameCDATA #IMPLIED name of digital file assigned by scanning technician(e.g. sopranos.jpg) Format CDATA #IMPLIED file format (e.g. JPEG, TIFF,PPT) Physical Location CDATA #IMPLIED archival location of originaltransparency or print Server Location CDATA #IMPLIED location of digitalasset storage system Digitizing Date CDATA #IMPLIED date digital assetwas scanned (date field) Creator CDATA #IMPLIED name of person creatingthe digital file (e.g. scanning technician) Filesize CDATA #IMPLIED sizeof digital file (KB/MB) Mode CDATA #IMPLIED color space (e.g. RGB, CMYK,Grayscale) Height_Inches CDATA #IMPLIED height of digital image (inches)Width_Inches CDATA #IMPLIED width of digital image (inches)Height_Pixels CDATA #IMPLIED height of digital image (pixels) Width(Pixesl0 CDATA #IMPLIED width of digital image (pixels) Resolution_DPICDATA #IMPLIED digital image resolution (dots per inch) > <!-DigitalAudio Metadata Structure-> <!ELEMENT Audio (audioMetadata,transactionMetadata)> <!ELEMENT audioMetadata (#PCDATA)> <! ATTLISTaudioMetadata AID CDATA #REQUIRED asset id PID CDATA #REQUIRED productID CID CDATA #REQUIRED contract id Title CDATA #IMPLIED audio titleMusic CDATA #IMPLIED yes or no Stock CDATA #IMPLIED yes or noStock_Library CDATA #IMPLIED music library information Stock_Sub_LibraryCDATA #IMPLIED audio library tracking information Stock_CD_Nbr CDATA#IMPLIED CD ID number Stock_CD_Title CDATA #IMPLIED CD title informationStock_Track_Title CDATA #IMPLIED audio track information Stock_DurationCDATA #IMPLIED length of media section Stock_Composer CDATA #IMPLIEDmusic composer information Stock_Publisher CDATA #IMPLIED publishingparty (ex. Warner, etc.) Stock_Society CDATA #IMPLIED (ex. ASCAP, etc.)Original CDATA #IMPLIED yes or no Original_Code CDATA #IMPLIED xOriginal_Session_Date CDATA #IMPLIED date of recording Original_ComposerCDATA #IMPLIED music composer information Original_Publisher CDATA#IMPLIED party of publisher (ex. Warner, etc.) Original_Society CDATA#IMPLIED x Rights_Issues CDATA #IMPLIED contract information (ex.Rights, Permissions) Contract_License CDATA #IMPLIED yes or no InternetCDATA #IMPLIED yes or no International CDATA #IMPLIED yes or noLibrary_Contact CDATA #IMPLIED contact person > <!-Long Form MovieMetadata Structure-> <!ELEMENT Movie (movie_FormatMetadata,TransactionMetadata)> <!ELEMENT movie_FormatMetadata (#PCDATA)> <!ATTLIST movie_FormatMetadata SAP CDATA #IMPLIED yes or no; secondaryaudio program (ex. Spanish) P_Version_Format CDATA #IMPLIED refers tothe format information (PRIME Table) Transmission_Format CDATA #REQUIREDdigital format (ex. MPEG, Quicktime, etc.) Storage_Capacity CDATA#IMPLIED storage requirements for digital transmission dataUnit_of_Measure_of_(—) CDATA #IMPLIED (ex. Megabytes MB, Gigabytes GB,Capacity Terabytes TB) Compression_Status CDATA #REQUIRED bit rateinformation ESP CDATA #REQUIRED yes or no Closed_Caption CDATA #IMPLIEDyes or no Sound CDATA #IMPLIED (ex. Stereo, Mono, Dolby, Dolby Digital,Dolby) >

Example 2 below shows a sample XML document generated as part of aphotographic asset search.

EXAMPLE 2

(filename: sample.xml) <?xml version=‘1.0’ standalone=‘no’?> <DAL><Asset> <Assetmetadata PID=“200000” AssetTitle=“Chaos Factor”Comments=“Soldiers talking to man”> </Assetmetadata> <Photo><Photometadata Resolution=“72 dpi” Talent=“Unknown”> </Photometadata></Photo> <Content>chaos_1_t.jpg </Content> </Asset> <Asset><Assetmetadata PID=“141896” AssetTitle=“lf walls could talk 2”Comments=“An HBO Films trilogy examining the lesbian experience inAmerica in three different decades”> </Assetmetadata> <Photo><Photometadata Resolution=“72 dpi” Talent=“Ellen Degeneres”></Photometadata> </Photo> <Content>walls_2_t.jpg </Content> </Asset><Asset> <Assetmetadata PID=“300000” AssetTitle=“Sex and the city”Comments=“Close up portrait of Sarah JessicaParker”> </Assetmetadata><Photo> <Photometadata Resolution=“72 dpi” Talent=Sarah and cast”></Photometadata> </Photo> <Content>sex_city_2_t.jpg </Content> </Asset><Asset> <Assetmetadata PID=“141897” AssetTitle=“If walls could talk 2”Comments=“ An HBO Films trilogy examining the lesbian experience inAmerica in three different decades”> </Assetmetadata> <Photo><Photometadata Resolution=“72 dpi” Talent=“Ellen Degeneres”></Photometadata> </Photo> <Content>walls_5_t.jpg </Content> </Asset></DAL>

XSL operates on XML search output. The output from XSL may be eitherHTML or XML both with CSS. Known software engines, such as, for example,a software engine known as XT developed by James Clark (seehttp://jclark.com/xml/xt.html for more details), can be used to convertXML into HTML. A sample command for doing such is: C:>XT sample.xmlcss.xsl output2.xml. This command generates an XML document namedoutput2.xml, which can be displayed using standard browser software.

Example 3a shows a sample XSL script. Example 3b shows a sample HTMLdocument generated by XSL on the XML search output of Example 2. Example3c shows a sample XML document with CSS also generated by XSL on the XMLsearch output of Example 2.

EXAMPLE 3a

<?xml version=“1.0”?> <xsl:stylesheet version=“1.0”xmlns:xsl=“http://www.w3.org/1999/XSL/Transform”> <xsl:templatematch=“/”> <xsl:apply-templates/> </xsl:template> </xsl:templatematch=“/DAL/Asset”> <TABLE WIDTH=“100%” BORDER=“1”><TR><TD HEIGHT=“288”><B>PID:</B><xsl:value-of select-Assetmetadata/@PID/><BR/> <B>AssetTitle: </B><xsl:value-of select=“Assetmedatada/@AssetTitle”/><BR/><B>Comments:</B><xsl:value-of select=“Assetmetadata/@Comments”/><BR><B>Resolution:</B><xsl:value-ofselect=“Photo/Photometadata/@Resolution”/><BR/><B>Talent:</B><xsl:value-of select=“Photo/Photometadata/@Talent”/><BR/></TD><TD WIDTH=“288” HEIGHT=“288”> <xsl:apply-templates/> </TD></TR><TABLE> </xsl:template> <xsl:template match=“/DAL/Asset/Content”> <P><Ahref=“{concat(‘full_’,ancestor::Asset/Content)}”><imgsrc=“{ancestor::Asset/Content}” border=“0”/> </A></P> </xsl:template></xsl:stylesheet>

EXAMPLE 3b

<HTML> <TABLE WIDTH=“100%” BORDER=“1”><TR> <TD HElGHT=“288”> <B>PID:</B>200000<BR/> <B>Asset Title:</B>Chaos Factor<BR/><B>Comments:</B>Soldiers talking to man<BR/> <B>Resolution:/B> 72dpi<BR/> <B>Talent:</B>Unknown<BR/> </TD> .TD WIDTH=“288” HEIGHT=“288”><P><A href=“full_chaos_1_t.jpg“<>img src=“chaos_l_t.jpg”border=“0”/></A></P></TD> </TR></TABLE> <TABLE WIDTH=“100%”BORDER=“1”><TR> <TD HEIGHT=“288”> <B>PID: </B>141896<BR/> <B>AssetTitle:</B>If walls could talk 2<BR/> <B>Comments:</B>An HBO Filmstrilogy examining the lesbian experience in America in three differentdecades<BR/> <B>Resolution:</B> 72 dpi<BR/> <B>Talent:</B>EllenDegeneres<BR/></TD> <TD WIDTH=“288” HEIGHT=“288”> <P><Ahref=full_walls_2_t.jpg”><imgsrc=“walls_2_t.jpg”border=“0”/></A></P></TD> </TR></TABLE> <TABLEWTDTH=“100%” BORDER=“1”><TR> <TD HEIGHT=“288”><B>PID: </B>300000<BR/><B>Asset Title:</B>Sex and the city<BR/> <B>Comments:</B>Close upportrait of Sarah Jessica Parker<BR/> <B>Resolution:</B> 72 dpi<BR/><B>Talent:</B>Sarah and cast<BR/></TD> <TD WTDTH=“288” HEIGHT=“288”><P><A href=“full_sex_city_2_t.jpg”><img src=“sex_city_t.jpg” border=“0”/></ A></P> </TD></TR></TABLE> <TABLE WlDTH=“100%” BORDER=“1”><TR> <TDHEIGHT=“288”> <B>PID: </B>141896<BR/> <B>Asset Title:</B>If walls couldtalk 2<BR/> <B>Comments:</B>An HBO Films trilogy examining the lesbianexperience in America in three different decades<BR/> <B>Resolution:</B>72 dpi<BR/> <B>Talent:</B>Ellen Degeneres<BR/></TD> <TD WIDTH=“288”HEIGHT=“288”> <P><A href=“full_walls_5_t.jpg”> <imgsrc=“walls_5_t.jpg”border=“0”/></ A></P> </TD> </TR></TABLE> </HTML>

EXAMPLE 3c

(filename: css.xml) <?xml version=1.0”?> <xsl:stylesheet version=“1.0”xmlns:xsl=“http://www.w3.org/1999/xsl/transform”> <xsl:templatematch=“/”> <xsl:processing-instructionname=“xml-stylesheet”>type=“text/css” href=“#photos” </xsl :processing-instruction> <xsl:apply-templates select=“DAL”/><xsl:template> <xsl:template match=“.”> <xsl:copy><xsl:value-ofselect=“.”/></xsl:copy> </xsl:template> <xsl:template match=“DAL”><style id=photos”> Asset {display: block;position:relative;width:100%;height:225px; border:inset3px gray;}Assetmetadata {display:inline;font-size:14pt;} Photo{display:inline;font-size:12pt;} Photometadata{display:inline;font-size: 12pt;} Content {width:72 px;height:72px;position:relative;display:block;float:left;} <xsl:for-eachselect=“//Asset”>Content[photo<xs1:value-of select=“@PID”/>]{background-image:url(<xsl:value-of select=“Content”/>);}</xsl:for-each> </style> <xsl:apply-templates select=“Asset”/></xsl:template> <xsl:template match=“/DAL/Asset/Content”> <Content id=“{concat(Photo', sibling::Assetmetadata/@PID)}href=“{sibling::Asset/Content}”/> </xsl:template> <xsl:templatematch=“/DAL/Asset”> <TABLE WIDTH=“100%” BORDER=“1”><TR><TD HEIGHT=“288”><B>PID: </B><xsl:value-of select=Assetmetadata/@PID/><BR/> <B>AssetTitle:</B> <xsl:value-of select=“Assetmetadata/@AssetTitle”/><BR/><B>Comments:</B><xsl:value-of select=“Assetmetadata/@Comments”/><BR/><B>Resolution:</B><xsl:value-ofselect=“Photo/Photometadata/@Resolution”/><BR/><B>Talent:</B><xsl:value-of select=Photo/Photometadatal@Talent”/>< BR/></TD> <TD WIDTH=“288” HEIGHT=“288”> <xsl:apply-templates /> </TD></TR></TABLE> </xsl:template> <xsl:template match=“/DAL Asset/Content”><P><A href={“concat(‘photo’,sibling::asset/content)}”> <imgsrc=“{ancestor::Asset/Content}” border=“0”/> </A></P> </xsl:template></xsl:stylesheet>

Thus it is seen that XML data definitions for digital assets areprovided that can be used as a standardized dictionary for applicationand platform independent exchange and repurposing of those assets. Oneskilled in the art will appreciate that the present invention can bepracticed by other than the described embodiments, which are presentedfor purposes of illustration and not of limitation, and the presentinvention is limited only by the claims which follow.

1. A computer readable storage medium storing computer-executableinstructions that are executed by a computer for performing steps of:storing data in a memory, the data comprising a server applicationprogram and only one single document type definition (DTD) for use instoring, retrieving, searching, or tracking at least three differenttypes of digital assets stored in a single database, each digital assetof the digital assets includes content and metadata, the metadataincludes rights management information, the server application programincluding modules for a parser, a query language utility, and a stylesheet processor; receiving a demand containing user entered searchparameters for information pertaining to the at least three differenttypes of the digital assets; accessing the DTD that defines declaredelements for the at least three different types of the digital assets,wherein the DTD further defines elements and attributes for rightsmanagement of the at least three different types of the digital assets,the at least three different types of the digital assets includingphotographs, audio recordings and at least one of promo, videorecordings, and voiceover digital assets, wherein the rights managementelements and attributes comprise metadata for at least one of: acontract identifier, an availability start date, an availability enddate, an allowed number of plays per agreement, a copyright holderidentifier, and a worldwide rights identifier, wherein the DTD definesmetadata for the photographs and metadata attributes for the photographsmetadata, the photographs metadata attributes comprising at least one ofa definition for black/white, a definition for color, a definition forcaption, and a definition for legal restrictions, wherein the DTDdefines metadata for the audio recordings and metadata attributes forthe audio recordings metadata, the audio recordings metadata attributescomprising a definition for rights issues regarding use of an audiorecording; converting, by using the query language utility, the demandcontaining user entered search parameters for information pertaining tothe digital assets into a query to be transmitted to the database,wherein the query language utility is a structured query language (SQL)utility and the style sheet processor is an extensible style sheetlanguage (XSL) processor; searching the at least three different typesof the digital assets based on the converted demand and the accessedDTD; and converting, by using the style sheet processor, search resultsreturned from the database into a style sheet for input to a clientapplication and displaying the converted search results to a user.
 2. Amethod for retrieving and tracking different types of assets, the methodcomprising: storing data in a memory that is read by a computer, thedata comprising a server application program and only one singledocument type definition (DTD) for use in storing, retrieving,searching, or tracking at least three different types of digital assetsstored in a single database, each digital asset of the digital assetsincludes content and metadata, the metadata includes rights managementinformation, the server application program includes modules for aparser, a query language utility, and a style sheet processor; receivinga demand containing user entered search parameters for informationpertaining to the at least three different types of the digital assets;accessing the DTD that defines declared elements for the at least threedifferent types of the digital assets by executing the serverapplication program, wherein the DTD further defines elements andattributes for rights management of the at least three different typesof the digital assets, the at least three different types of the digitalassets including photographs, audio recordings and at least one ofpromo, video recordings, and voiceover digital assets, wherein therights management elements and attributes comprise metadata for at leastone of: a contract identifier, an availability start date, anavailability end date, an allowed number of plays per agreement, acopyright holder identifier, and a worldwide rights identifier, whereinthe DTD defines metadata for the photographs and metadata attributes forthe photographs metadata, the photographs metadata attributes comprisingat least one of a definition for black/white, a definition for color, adefinition for caption, and a definition for legal restrictions, whereinthe DTD defines metadata for the audio recordings and metadataattributes for the audio recordings metadata, the audio recordingsmetadata attributes comprising a definition for rights issues regardinguse of an audio recording; converting, by using the query languageutility, the demand containing user entered search parameters forinformation pertaining to the digital assets into a query to betransmitted to the database, wherein the query language utility is astructured query language (SQL) utility and the style sheet processor isan extensible style sheet language (XSL) processor; searching the atleast three different types of the digital assets based on the converteddemand and the accessed DTD; and converting, by using the style sheetprocessor, search results returned from the database into a style sheetfor input to a client application and displaying the converted searchresults to a user.
 3. A computer system for retrieving assets, thesystem comprising: a server comprising application software and a singledatabase, the database storing a plurality of digital assets ofdifferent types, the different types including photographs, movies,audio recordings, video recordings, graphics, and text documents, eachdigital asset of the digital assets comprising content and metadata, themetadata comprising rights management information, the applicationsoftware includes modules for a parser, a query language utility, and astyle sheet processor; a first computer readable storage mediumcomprising only one single document type definition (DTD) accessible bythe server application software, the DTD defining data structure of eachdifferent type of the digital assets stored in the database; a secondcomputer readable storage medium comprising search and retrievalsoftware for searching and retrieving one or more of the different typesof the digital assets from the database and further comprisingcomputer-executable instructions that are executed by a computer to:receive a demand containing user entered search parameters forinformation pertaining to at least three different types of the digitalassets; access the DTD that defines declared elements for the at leastthree different types of the digital assets, wherein the DTD furtherdefines elements and attributes for rights management of the at leastthree different types of the digital assets, the at least threedifferent types of the digital assets including the photographs, theaudio recordings and at least one of promo, video recordings, andvoiceover digital assets, wherein the rights management elements andattributes comprise metadata for at least one of: a contract identifier,an availability start date, an availability end date, an allowed numberof plays per agreement, a copyright holder identifier, and a worldwiderights identifier, wherein the DTD defines metadata for the photographsand metadata attributes for the photographs metadata, the photographsmetadata attributes comprising at least one of a definition forblack/white, a definition for color, a definition for caption, and adefinition for legal restrictions, wherein the DTD defines metadata forthe audio recordings and metadata attributes for the audio recordingsmetadata, the audio recordings metadata attributes comprising adefinition for rights issues regarding use of an audio recording;convert, by using the query language utility, the demand containing userentered search parameters for information pertaining to the digitalassets into a query to be transmitted to the database, wherein the querylanguage utility is a structured query language (SQL) utility and thestyle sheet processor is an extensible style sheet language (XSL)processor; search the at least three different types of the digitalassets based on the converted demand and the accessed DTD; and convert,by using the style sheet processor, search results returned from thedatabase into a style sheet for input to a client application anddisplaying the converted search results to a user.